Closes _____

Problem

The original jabrefHost.py script was hardcoded to look for JabRef in the standard macOS installation folder (/Applications/JabRef.app). Since I am developing and running JabRef from the source code (using Gradle), I don't have a packaged app installed there. This caused the Native Messaging host to fail because it couldn't find the executable.

Solution

I modified jabrefHost.py to add a development path check. The script now looks for the executable in two places:
1. First: It checks my local build folder (jabgui/build/install/jabgui/bin/JabRef).
2. Second: It falls back to the standard system path

Result

This allows us to test the browser extension against the latest code changes I make in the IDE immediately, without needing to package and install the full application every time I change a line of code. It streamlines the development loop significantly.

Steps to test

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• [.] I manually tested my changes in running JabRef (always required)
• [.] I added JUnit tests for changes (if applicable)
• [.] I added screenshots in the PR description (if change is visible to the user)
• [.] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• [.] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.